-
Notifications
You must be signed in to change notification settings - Fork 3
Conversation
Exception: (UVM global queu) > comm is 16 bytes (including the \0), so 15 characters. So as an > example of /proc/stat, this was actually right :-)
c0cc3c2
to
8a8c1ab
Compare
8a8c1ab
to
1731eaf
Compare
Sorry, accidentally push to master, causing GitHub to mark this as resolved. I reverted the old state and re-opened the merge/pull request. |
No commits here? I'm only on mobile phone today, so I'm a bit disabled and can't investigate. |
1731eaf
to
7c86fbc
Compare
1731eaf
to
03bd205
Compare
Sorry, looks like, it’s not so easy to re-open a merge/pull request. |
mx_proc.c
Outdated
char linebuf[256]; // "2147483647 (max128chars) X 2147483647 " = 156 | ||
char linebuf[64]; // "2147483647 (max15chars) X 2147483647 " = 43 | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
comm being 15 seems like a very wrong assumption ;) also not scope of fixing spelling ;)
kworker/4:0H-events_highpri
is a valid value in there and is longer than 15.. so that those are truncated to 16 (not 15) is out of date documentation i assume..
also why safe minimum amount of bytes and risk failure ;)
1731eaf
to
03bd205
Compare
Thank you all for the review and comments. Let’s split the controversial commit out: #117. |
No description provided.